Information management systems with time zone information, including event scheduling processes

ABSTRACT

Information management systems with time zone information, including event scheduling processes are disclosed. One aspect of the invention is directed toward a computer-implemented scheduling method that can include identifying a difference between a participant time zone and a user time zone, reviewing availability information for the participant and/or one or more selected time preference periods for the participant, and selecting a time range for an event. The method can further include reviewing one or more selected time preference periods for the user. Another aspect of the invention is directed toward a computer-implemented method for associating time zone information with a contact in an information management program application that includes selecting a contact, analyzing contact information associated with the contact, and determining a time zone for the contact based on the analysis of the contact information.

CROSS REFERENCE TO RELATED APPLICATION(S)

This application is a continuation application of U.S. patentapplication Ser. No. 15/827,490, filed on Nov. 30, 2017, and entitled“INFORMATION MANAGEMENT SYSTEMS WITH TIME ZONE INFORMATION, INCLUDINGEVENT SCHEDULING PROCESSES,” which is a continuation of U.S. Pat. No.9,864,975, issued on Jan. 9, 2018, entitled “INFORMATION MANAGEMENTSYSTEMS WITH TIME ZONE INFORMATION, INCLUDING EVENT SCHEDULINGPROCESSES,” which is a continuation of U.S. Pat. No. 9,542,670, issuedon Jan. 10, 2017, entitled “INFORMATION MANAGEMENT SYSTEMS WITH TIMEZONE INFORMATION, INCLUDING EVENT SCHEDULING PROCESSES,” which is acontinuation of U.S. Pat. No. 8,959,147, issued on Feb. 17, 2015,entitled “INFORMATION MANAGEMENT SYSTEMS WITH TIME ZONE INFORMATION,INCLUDING EVENT SCHEDULING PROCESSES,” which is a continuation of U.S.Pat. No. 7,856,483, issued on Dec. 21, 2010, entitled “INFORMATIONMANAGEMENT SYSTEMS WITH TIME ZONE INFORMATION, INCLUDING EVENTSCHEDULING PROCESSES,” which are incorporated herein in their entiretyby reference.

TECHNICAL FIELD

The following disclosure relates generally to information managementsystems with time zone information, including event scheduling processeshaving time zone information.

BACKGROUND

Today's global economy demands effective worldwide communication. Forexample, manufacturers often have suppliers located across the countryand around the world. Timely and effective communication between themanufacturer and suppliers can be critical to business success. In othercases, companies often assign business projects to work groups withmembers physically located around the world. In some situations, thework group members can belong to different organizations and/orcompanies. As with manufacturers and suppliers, timely and effectivecommunication can be critical to the success of the work group.

Telecommunications and other technologies, such as email,video-conferencing, and internet meetings provide timely and effectiveworldwide communication twenty-four hours a day, seven days a week.However, because of the difference in local time from one location tothe next, certain forms of communication may not be appropriate duringcertain times of the day. For example, when the local time is 1700 hourson the west coast of the United States, it can be 0200 hours in Germany.Accordingly, when calling or scheduling a meeting (e.g., internetmeeting or video conference) with a business associate, it has becomeincreasingly important to consider the business associate's local time.However, it can be difficult to effectively and efficiently ascertainand/or track the different time zones for multiple business associatesin today's complex business environment.

SUMMARY

The present invention is directed generally toward informationmanagement systems with time zone information, including eventscheduling processes. One aspect of the invention is directed toward acomputer-implemented scheduling method that includes identifying adifference between a participant time zone and a user time zone,reviewing availability information for the participant and/or one ormore selected time preference periods for the participant, and selectinga time range for an event. The participant time zone is a time zoneassociated with a participant and the user time zone is a time zoneassociated with a user who is scheduling the event. The method canfurther include reviewing one or more selected time preference periodsfor the user. These time preference periods can include preferred timesfor scheduling events or periods of time during which the scheduling ofevents is discouraged. The method can also include coordinating the timerange for the event with a user schedule and/or a participant schedule(e.g., annotating the user and/or participant schedule with the eventduring the selected time range).

Another aspect of the invention is directed toward acomputer-implemented method for associating time zone information with acontact in an information management program application that includesselecting a contact, analyzing contact information associated with thecontact, and determining a time zone for the contact based on theanalysis of the contact information. For example, the contact's phonenumber, address, and/or affiliations can be used to determine or suggesta time zone that can be associated with the contact. The method canfurther include storing the time zone for the contact. The time zoneinformation for the contact can be used to aid a user in scheduling anevent.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a partially schematic illustration of a computing systemsuitable for implementing embodiments of the invention.

FIG. 2 is a flow diagram illustrating a computer-implemented schedulingprocess in accordance with embodiments of the invention.

FIG. 3 is a partially schematic diagram of a computing systemenvironment, similar to the computing system environment shown in FIG.1, having multiple computers suitable for implementing embodiments ofthe invention.

FIG. 4 is a flow diagram illustrating a computer-implemented schedulingprocess in accordance with further embodiments of the invention.

FIG. 5 is a partially schematic illustration of a display identifying adifference between participant time zones and a user time zone inaccordance with embodiments of the invention.

FIG. 6 is a partially schematic illustration of a display identifying adifference between participant time zones and a user time zone inaccordance with other embodiments of the invention.

FIG. 7 is a flow diagram illustrating still further embodiments of thecomputer-implemented scheduling process shown in FIG. 2.

FIG. 8 is a flow diagram illustrating yet other embodiments of thecomputer-implemented scheduling process shown in FIG. 2.

FIG. 9 is a flow diagram illustrating a computer-implemented process forassociating time zone information with a contact in an informationmanagement program application in accordance with certain embodiments ofthe invention.

FIG. 10 is a flow diagram illustrating a computer-implemented processfor associating time zone information with a contact in an informationmanagement program application in accordance with other embodiments ofthe invention.

FIG. 11 is a partially schematic illustration of an informationmanagement program application display of contact information inaccordance with embodiments of the invention.

FIG. 12 is a partially schematic illustration of another informationmanagement program application display of contact information inaccordance with other embodiments of the invention.

FIG. 13 is a flow diagram illustrating still other embodiments of thecomputer-implemented scheduling process shown in FIG. 2.

DETAILED DESCRIPTION

The following disclosure describes several embodiments of informationmanagement systems with time zone information, including eventscheduling processes. Specific details of several embodiments of theinvention are described below to provide a thorough understanding ofsuch embodiments. However, other details describing well-knownstructures and routines often associated with computer-based informationmanagement systems are not set forth below to avoid unnecessarilyobscuring the description of the various embodiments. Additionally,several flow diagrams and processes having process portions aredescribed to illustrate various embodiments of the invention. It will berecognized, however, that these process portions can be performed in anyorder, and are not limited to the order described herein with referenceto particular embodiments. Furthermore, those of ordinary skill in theart will understand that the invention may have other embodiments thatinclude additional elements or lack one or more of the elementsdescribed below with reference to FIGS. 1-13.

FIG. 1 illustrates an example of a suitable computing system environment100 on which the invention may be implemented. The computing systemenvironment 100 is only one example of a suitable computing environmentand is not intended to suggest any limitation as to the scope of use orfunctionality of the invention. Neither should the computing environment100 be interpreted as having any dependency or requirement relating toany one or combination of components illustrated in the exemplaryoperating environment 100.

The invention is operational with numerous other general purpose orspecial purpose computing system environments or configurations.Examples of well known computing systems, environments, and/orconfigurations that may be suitable for use with the invention include,but are not limited to, personal computers, server computers, hand-heldor laptop devices, multiprocessor systems, microprocessor-based systems,set top boxes, programmable consumer electronics, network PCs,minicomputers, mainframe computers, distributed computing environmentsthat include any of the above systems or devices, and the like.

The invention may be described in the general context ofcomputer-executable instructions, such as program modules, beingexecuted by a computer. Generally, program modules include routines,programs, objects, components, data structure, etc. that performparticular tasks or implement particular abstract data types. Theinvention may also be practiced in distributed computing environmentswhere tasks are performed by remote processing devices that are linkedthrough a communications network. In a distributed computingenvironment, program modules may be located in both local and remotecomputer storage media including memory storage devices.

With reference to FIG. 1, an exemplary system for implementing theinvention includes a general purpose computing device in the form of acomputer 110. Components of computer 110 may include, but are notlimited to, a processing unit 120, a system memory 130, and a system bus121 that couples various system components including the system memoryto the processing unit 120. The system bus 121 may be any of severaltypes of bus structures including a memory bus or memory controller, aperipheral bus, and a local bus using any of a variety of busarchitectures. By way of example, and not limitation, such architecturesinclude Industry Standard Architecture (ISA) bus, Micro ChannelArchitecture (MCA) bus, Enhanced ISA (EISA) bus, Video ElectronicsStandards Association (VESA) local bus, and Peripheral ComponentInterconnect (PCI) bus also known as Mezzanine bus.

Computer 110 typically includes a variety of computer-readable media.Computer-readable media can be any available media that can be accessedby computer 110 and includes both volatile and nonvolatile media,removable and non-removable media. By way of example, and notlimitation, computer-readable media may comprise computer storage mediaand communication media. Computer storage media includes both volatileand nonvolatile, removable and non-removable media implemented in anymethod or technology for storage of information such ascomputer-readable instructions, data structures, program modules orother data. Computer storage media includes, but is not limited to, RAM,ROM, EEPROM, flash memory or other memory technology, CD-ROM, digitalversatile disks (DVD) or other optical disk storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,or any other medium which can be used to store the desired informationand which can be accessed by computer 110. Communication media typicallyembody computer-readable instructions, data structures, program modulesor other data in a modulated data signal such as a carrier wave or othertransport mechanism and includes any information delivery media. Theterm “modulated data signal” means a signal that has one or more of itscharacteristics set or changed in such a manner as to encode informationin the signal. By way of example, and not limitation, communicationmedia includes wired media such as a wired network or direct-wiredconnection, and wireless media such as acoustic, RF, infrared and otherwireless media. Combinations of the any of the above should also beincluded within the scope of computer-readable media. It will berecognized that any or all of the process portions described herein canbe stored on computer-readable media.

The system memory 130 includes computer storage media in the form ofvolatile and/or nonvolatile memory such as read only memory (ROM) 131and random access memory (RAM) 132. A basic input/output system 133(BIOS), containing the basic routines that help to transfer informationbetween elements with computer 110, such as during start-up, istypically stored in ROM 131. RAM 132 typically contains data and/orprogram modules that are immediately accessible to and/or presentlybeing operated on by processing unit 120. By way of example, and notlimitation, FIG. 1 illustrates operating system 134, applicationprograms 135, other program modules 136, and program data 137.

The computer 110 may also include other removable/non-removable,volatile/nonvolatile computer storage media. By way of example only,FIG. 1 illustrates a hard disk drive 140 that reads from or writes tonon-removable, nonvolatile magnetic media, a magnetic disk drive 151that reads from or writes to a removable, nonvolatile magnetic disk 152,and an optical disk drive 155 that reads from or writes to a removable,nonvolatile optical disk 156 such as a CD ROM or other optical media.Other removable/non-removable, volatile/nonvolatile computer storagemedia that can be used in the exemplary operating environment include,but are not limited to, magnetic tape cassettes, flash memory cards,digital versatile disks, digital video tape, solid state RAM, solidstate ROM, and the like. The hard disk drive 141 is typically connectedto the system bus 121 through a non-removable memory interface such asinterface 140, and magnetic disk drive 151 and optical disk drive 155are typically connected to the system bus 121 by a removable memoryinterface, such as interface 150.

The drives and their associated computer storage media, discussed aboveand illustrated in FIG. 1, provide storage of computer-readableinstructions, data structures, program modules and other data for thecomputer 110. In FIG. 1, for example, hard disk drive 141 is illustratedas storing operating system 144, application programs 145, other programmodules 146, and program data 147. Note that these components can eitherbe the same as or different from operating system 134, applicationprograms 135, other program modules 136, and program data 137. Operatingsystem 144, application programs 145, other program modules 146, andprogram data 147 are given different numbers here to illustrate that, ata minimum, they are different copies.

A user may enter commands and information into the computer 110 throughinput devices such as a keyboard 162 and pointing device 161, commonlyreferred to as a mouse, trackball or touch pad. Other input devices (notshown) may include a microphone, joystick, game pad, satellite dish,scanner, or the like. These and other input devices are often connectedto the processing unit 120 through a user input interface 160 that iscoupled to the system bus, but may be connected by other interface andbus structures, such as a parallel port, game port, or a universalserial bus (USB). A monitor 191 or other type of display device is alsoconnected to the system bus 121 via an interface, such as a videointerface 190. In addition to the monitor, computers may also includeother peripheral output devices such as speakers 197 and printer 196,which may be connected through an output peripheral interface 195.

The computer 110 may operate in a networked environment using logicalconnections to one or more remote computers, such as a remote computer180. The remote computer 180 may be a personal computer, a server, arouter, a network PC, a peer device, or other common network node, andtypically includes many or all of the elements described above relativeto the computer 110, although only a memory storage device 181 has beenillustrated in FIG. 1. The logical connections depicted in FIG. 1include a local area network (LAN) 171 and a wide area network (WAN)173, but may also include other networks. Such networking environmentsare commonplace in offices, enterprise-wide computer networks, intranetsand the Internet.

When used in a LAN networking environment, the computer 110 is connectedto the LAN 171 through a network interface or adapter 170. When used ina WAN networking environment, the computer 110 typically includes amodem 172 or other means for establishing communications over the WAN173, such as the Internet. The modem 172, which may be internal orexternal, may be connected to the system bus 121 via the user inputinterface 160, or other appropriate mechanism. In a networkedenvironment, program modules depicted relative to the computer 110, orportions thereof, may be stored in the remote memory storage device. Byway of example, and not limitation, FIG. 1 illustrates remoteapplication programs 185 as residing on memory device 181. It will beappreciated that the network connections shown are exemplary and othermeans of establishing a communications link between the computers may beused.

Certain embodiments of the present invention are directed towardcomputer-implemented scheduling processes using an informationmanagement system application, for example, using “Microsoft® Outlook®,”available from the Microsoft Corporation of Redmond, Wash. Manyinformation management systems applications or personal informationmanagement system applications can store contacts (e.g., names of peopleor organizations) and contact information. Contact information caninclude the contacts' names, identification (e.g., identifyinginformation regarding how the contacts are listed or identified),physical addresses, phone numbers, email addresses, and/or affiliations(e.g., an organization, a company, and/or a portion of the company towhich the contact belongs or works). Additionally, many informationmanagement system applications have note, task, email, and/or calendarfunctions. In some cases, the calendar function can be used to aid inscheduling meetings or other events.

When scheduling an event (e.g., a phone call, video conference, and/orinternet meeting) it can be important to consider the local time foreach of the individuals involved. For example, if one individual is onthe west coast of the United States and another individual is inGermany, the local time for each individual can differ by nine hours.This could result in a video conference being scheduled for 1500 (e.g.,1500 hours) on the west coast of the United States and for 0000 for theindividual in Germany.

Accordingly, FIG. 2 illustrates a computer-implemented schedulingprocess 200 that includes identifying a difference between a participanttime zone and a user time zone, wherein the participant time zone isassociated with a participant and the user time zone is associated witha user scheduling an event (process portion 202), reviewing availabilityinformation for the participant and/or one or more selected timepreference periods for the participant (process portion 204), andselecting a time range for the event (process portion 206). Availabilityinformation can include when an individual (e.g., participant) isavailable to potentially attend an event (e.g., free) and/or when theindividual is scheduled for other events, tentatively scheduled forother events, and/or otherwise busy. A selected time preference periodcan include time periods during which events should be scheduled (e.g.,normal business hours) and/or time periods during which the schedulingevents should be avoided (e.g., during the middle of the night). A timerange can include a single time (e.g., an event scheduled for 1315 inthe user time zone) or a range of time during which an event is expectedto occur. This process 200 can allow the user to be aware of theparticipant time zone and the associated local time to determine whetherthe selected time range falls during an acceptable portion of the dayfor the participant (e.g., during normal business hours).

As discussed above, the process portions can be accomplished in anyorder. For example in one embodiment, the process portions can beaccomplished in the order they are listed. In another embodiment, theavailability of the participant and/or one or more of the selected timepreference periods for the participant can be reviewed (process portion204), the time range for an event can be selected (process portion 206),and then the difference between the participant time zone and a usertime zone can be identified (process portion 202). If the selected timerange is unsuitable based on the difference between the time zones, theuser can then schedule the event for another time range by repeating theprocess.

In certain embodiments, as discussed below with reference to FIGS. 5 and6, identifying the difference between the participant time zone and theuser time zone (process portion 202) can include graphically displayinga time difference between the participant time zone and the user timezone to the user (process portion 208). In other embodiments,identifying the difference between the participant time zone and theuser time zone (process portion 202) can be accomplished in other ways.For example, in certain embodiments the time difference can be shownnumerically as a number of hours ahead or behind the user time zone oras the difference between local time and Universal Coordinated Time.

In other embodiments, as discussed below with reference to FIGS. 5 and6, reviewing availability information and/or one or more selected timepreference periods for the participant can include graphicallydisplaying the availability information and/or one or more of theselected time preference periods for the participant relative to theparticipant time zone (process portion 210). In other embodiments,reviewing availability information and/or one or more selected timepreference periods for the participant (process portion 204) can beaccomplished in other ways. For example, in certain embodiments theavailability information and/or one or more selected time preferenceperiods for the participant can be displayed in a list. In certainembodiments, the process can further include reviewing availabilityinformation and/or one or more selected time preference periods for theuser (process portion 212), for example, when the user will participatein the event. Availability information for the participant, selectedtime preference period(s) for the participant, availability informationfor the user, and/or selected time preference period(s) for the user canbe stored in a computing system environment (e.g., the computing systemenvironment 100 shown in FIG. 1), including on the user's computer, theparticipant's computer, and/or on a server (process portion 214).

This general process can be used for any number of participants. Forexample, as shown in FIG. 3, a computing system environment 300 (similarto the computing system environment 100, shown in FIG. 1) includes acommunication network 310 that connects a user's computer 320, a firstparticipant's computer 330, a first additional participant's computers340 a, and a second additional participant's computer 340 b. The usercan be associated (e.g., located or based in) a first time zone (e.g.,U.S. Pacific Time). The first participant can be associated with asecond time zone (e.g., U.S. Eastern Time). The first additionalparticipant can be associated with a third time zone (e.g., U.S. CentralTime) and the second additional participant can be associated with afourth time zone (e.g., U.S. Mountain Time). In other embodiments, therecan be more or fewer additional participants.

Accordingly, as illustrated in FIG. 4, a computer-implemented schedulingmethod 400 can include identifying a difference between a firstparticipant time zone and a user time zone, wherein the firstparticipant time zone is associated with a first participant and theuser time zone is associated with a user scheduling an event (processportion 402). The method can further include identifying a differencebetween one or more additional participant time zones at least one ofthe first participant time zone and the user time zone, wherein each ofthe one or more additional participant time zones is associated with anadditional participant (process portion 404). The method can stillfurther include reviewing availability information and/or one or moreselected time preference periods for the first participant (processportion 406), reviewing availability information and/or one or moreselected time preference periods for each of the additional participants(process portion 408), and selecting a time range for the event (processportion 410).

FIG. 5 is a partially schematic illustration of a display 560identifying a difference between participant time zones and a user timezone in accordance with embodiments of the invention. In FIG. 5, theuser and participant identifications 562 are listed along a side of thedisplay 560. The user and participant time zone identifications 564 arelisted next to the user and participant identifications 562. This canserve to identify a difference in time zones between the user and/orparticipants. A time scale 566 is listed across the top of the display.The difference between morning and afternoon can be indicated by variousmethods, including color coding, shading, the use of textures, the useof symbols, and/or displaying the time in a twenty-four hour format. Inthe illustrated embodiment, the time is displayed in the twenty-fourhour format.

Various methods (e.g., using shading, using texturing, using symbols,using colors, and/or using lists) can be used to show availabilityinformation for a participant or user. In the illustrated embodiment, anon-availability symbol 572 shows that the first participant (1 PART) isunavailable between 1500 and 1700 Pacific Time. Accordingly, the userknows not to schedule an event between 1500 and 1700 Pacific Time if thefirst participant is required to participate in the event. Variouslevels of availability can also be shown. For example, in one embodimenta selected symbol can indicate that the user or participant istentatively unavailable and a different symbol can be used to show theuser or participant is unavailable. In the illustrated embodiment, theuser and participant availabilities are all shown relative to the user'stime zone (e.g., the Pacific Time Zone). Other embodiments can haveother arrangements, as discussed below in further detail.

The selected time range bars 568 indicate a time range of 1830 to 1930,relative to the user's time zone (e.g., Pacific Time), has beenselected. Because the non-availability symbols 572 are shown withreference to the user time zone and no non-availability symbols appearwithin the confines of the scheduling bars 568, neither the user norparticipants have indicated non-availability during the selected timerange. The time range can be manually selected by the user based on theavailability of the participants and/or the user, or automaticallysuggested (e.g., an executable instruction configured to choose thefirst available time where all the participants or all the participantsand the user are available).

Time range indicators 574 show the time difference between the timezones of the user and the participants. For example, the user's timerange indicator 574 a is shown between the time range bars 568indicating a time range of 1830 to 1930 in the user time zone. The firstparticipant's time range indicator 574 b indicates that the selectedtime (1830 to 1930 Pacific Time) falls between 2130 and 2230 local timein the Eastern Time Zone. Similarly, the selected time (1830 to 1930Pacific Time) falls between 2030 and 2130 in the Central Time Zone asindicated by the first additional participant's time range indicator 574c and between 1930 and 2030 in the Mountain Time Zone as indicated bythe second additional participant's time range indicator 574 d.

If a participant were associated with the same time zone as the user,the display would show that the participant time zone identifier 564 isthe same as the user and the participant's time range indicator 574would be shown between the time range bars 568, indicating that the timedifference between the user time zone and the participant time zone iszero hours. In certain embodiments, the time zones are depicted only bythe time differences depicted by the time range indicators 574 and thetime zone identifiers 564 are not shown. In other embodiments, thedisplay of the difference between participant time zones and the usertime zone can have other arrangements.

For example, FIG. 6 illustrates a display 660 in accordance with anotherembodiment of the invention. In FIG. 6, the user and participantidentifications 662 are listed along a side of a display 660. The userand participant time zone identifiers 664 are listed beside the user andparticipant identifications 662 and can identify a difference betweenthe user time zone and/or the participant time zones.

In FIG. 6, the local time for each time zone is displayed relative tothe other time zones by the time scales 666. For example, the user'stime scale 666 a represents the time in the user time zone and runs from1600 to 2200. During the same period, the first participant's time scale666 b runs from 1900 to 0100 indicating the corresponding local time inthe first participant time zone. Similarly, the first additionalparticipant's time scale 666 c runs from 1800 to 0000 indicating thecorresponding local time in the first additional participant time zoneand the second additional participant's time scale 666 d runs from 1700to 2300 indicating the corresponding local time in the second additionalparticipant time zone. In other embodiments, the time zones are depictedonly by the time differences depicted on the time scales 666 and thetime zone identifiers 664 are not shown.

Accordingly, a user can identify a time difference between the varioustime zones by examining the display 660. Because the local time for eachtime zone is displayed, availability information can be shown in localtime for each participant, as illustrated by the non-availability symbol672 shown between 1900 and 2000 Eastern Time for the first participant.From examining the display, the user can determine that thenon-availability for the first participant corresponds to 1600 to 1700in the user time zone.

The selected time range is indicated for the user and participants bytime range indicators 674. The user time range indicator 674 a showsthat the selected time range runs between 1830 and 1930 in the user timezone. Correspondingly, the first participant's time range indicator 674b shows that the selected time range runs between 2130 to 2230 in thefirst participant time zone, the first additional participant's timerange indicator 674 c shows that the selected time range runs between2030 and 2130 in the first additional participant time zone, and thesecond participant's time range indicator 674 d shows that the selectedtime range runs between 1930 and 2030 in the second additionalparticipant time zone. Because the time zones are aligned to show thecorresponding local time for a selected time range, all of the timerange indicators 674 are aligned vertically on the display. In otherembodiments, the display can have other arrangements, for example thetime range bars 568, shown in FIG. 5, can also be used with the displayshown in FIG. 6.

As shown in process portion 204 (shown in FIG. 2), when scheduling anevent, it is sometimes desirable to consider time preference periods inaddition to, or in lieu of, availability information. Time preferenceperiods can include an individual's (e.g., a participant's) preferenceor expected preference regarding periods of time during which schedulingshould occur or should be avoided. For example, it may be preferred toschedule events during normal business hours and to avoid schedulingevents in the middle of the night. In certain embodiments these timepreferences can be selected by default, selected by the user, and/orselected by each participant (e.g., selected by the participant andincluded with the participant's availability information and/or contactinformation). In some embodiments, the user can override or adjust thepreferences (e.g., when a selected time preference period isautomatically suggested or selected by default). In certain embodiments,participants can have multiple time preference periods and/or differentlevels of time preference periods. For example, a participant can have afirst time preference period during which the scheduling of events willnot be accepted (e.g., during sleeping hours) and a second timepreference period during which the scheduling of events is discouraged(e.g., outside of normal business hours, but will likely be accepted).

Accordingly, as shown in FIG. 7, in certain embodiments reviewing one ormore selected time preference periods of the participant (processportion 204 in FIG. 2) can include indicating a selected time preferenceperiod for the participant in relationship to the participant time zone(process portion 702). In other embodiments, reviewing one or moreselected time preference periods for the participant can includeindicating that the selected time range is during one or more selectedtime preference periods for the participant in relationship to theparticipant time zone or is not during the one or more selected timepreference periods for the participant in relationship to theparticipant time zone (process portion 704). In still other embodiments,the computer-implemented scheduling process shown in FIG. 2 can includeselecting a time preference period for the participant in relationshipto the participant time zone and/or a time preference period for theuser in relationship to the user time zone (process portion 706). Forexample, as discussed above, a time preference period can be selected bydefault, by the participant, or by the user.

In yet other embodiments, the process can include reviewing one or moreselected time preference periods for the user by indicating a selectedtime preference period for the user in relationship to the user timezone (process portion 708). In still other embodiments, the process caninclude reviewing one or more selected time preference periods for theuse by indicating that the selected time range is during one or moreselected time preference periods for the user in relationship to theuser time zone or is not during the one or more selected time preferenceperiods for the user in relationship to the user time zone (processportion 710). In yet another embodiment, the process can includesuggesting a time range based on the availability information for theparticipant, availability information for the user, the participant timezone, the user time zone, one or more selected time preference periodsfor the participant, and/or one or more selected time preference periodsfor the user (process portion 712).

For example, referring back to FIG. 6, multiple time preference periods676 are shown. In FIG. 6, the first participant has a “no schedule” timepreference period 676 a shown between 2200 and 0100 local time. Thefirst additional participant has a “no schedule” time preference period676 b shown between 2200 and 0000, and a time preference period 676 cshown between 2000 and 2200 during which the scheduling of events isdiscouraged. Time preference periods can be indicated via variousmethods, including the use of color, the use of shading, the use ofsymbols, the use of textures, and/or the use of lists.

A portion of the first participant's time range indicator 674 b is shownin red because it extends into the first participant's “no schedule”time preference period 676 b. In other embodiments, other methods can beused to indicate the time range indicator 674 extends into a timepreference period 676 (e.g., symbols, textures, shading, and/oralphanumeric messages). In FIG. 6, the first additional participant'stime range indicator 674 c is unchanged even though it extends throughthe first additional participant's time preference period 676 c duringwhich the scheduling of events is discouraged.

In still other embodiments, other methods can be used to indicate timepreference periods. For example, referring back to FIG. 5, a portion ofthe first participant's time range indicator 574 a is red, indicatingthat the time range indicator 574 b extends into the first participant's“no schedule” time preference period. The first additional participanttime range indicator 574 c is amber, indicating that it extends throughthe first additional participant's time preference period during whichthe scheduling of events is discouraged. Accordingly, once a time isselected for an event, the user can have an indication of aparticipant's time preference periods.

Further embodiments of the invention are discussed below in detail. Manyof these embodiments are discussed with reference to a user and aparticipant. However, it will be recognized that many or all of theseembodiments can be applied to scheduling multiple participants, asdiscussed above.

FIG. 8 is a flow diagram illustrating further embodiments of thecomputer-implemented scheduling process shown in FIG. 2. The schedulingprocess, shown in FIG. 2, can also include collecting the participanttime zone (process portion 806). The collected participant time zone canthen be compared to the user time zone to identify a difference betweenthe participant time zone and the user time zone (process portion 202).Collecting the participant time zone can include at least one ofmanually entering a time zone, manually selecting a time zone from alist of time zones, retrieving a stored time zone associated with theparticipant, accepting a time zone associated with a phone number of theparticipant, accepting a time zone associated with an address of theparticipant, and accepting a time zone associated with an affiliation ofthe participant (process portion 808).

The scheduling process can further include storing the participant timezone (process portion 810) so that it can be retrieved and compared tothe user time zone. The time zone information can be stored anywhere ina computing system environment (e.g., the computing system environment100, shown in FIG. 1), including on a remote computer, in a systemmemory, and/or on a computer storage medium. For example, in oneembodiment, the time difference between Universal Coordinated Time and alocal time associated with the participant, stored on a participant'sremote computer, can be communicated to the user's computer and used todetermine a participant time zone. Similarly, the process can includestoring the user time zone (process portion 812) for use in identifyinga difference between the participant time zone and the user time zone.

In certain embodiments, the user can select a participant identification(e.g., a name, address, and/or email) from a list of contacts (processportion 814). The participant time zone can be stored as part of thecontact information or be associated with a portion of the contactinformation (e.g., associated with the contact information, but bestored elsewhere in the computing system). Accordingly, when the contactis selected, the participant time zone can be identified and compared tothe user time zone to identify the difference between the two.

To aid in time zone identification, a computer-implemented process forassociating time zone information with a contact in an informationmanagement program application can be used to identify a time zone whenthe contact information for a contact or contact identification isentered into the information management program application. Asdiscussed above, the time zone can be stored as part of the contactinformation or associated with the contact information and recalled at alater time if the contact is selected as a participant. In anotherembodiment, the process can use existing contact information to aid theuser in determining a time zone for a participant identificationselected from a contact list (e.g., when the participant identificationis selected during a scheduling process). In still further embodiments,the process can be used to aid a user in determining a user time zone(e.g., when the user enters user contact information into an informationmanagement program application).

FIG. 9 is a flow diagram illustrating a computer-implemented process 900for associating time zone information with a contact in an informationmanagement program application in accordance with embodiments of theinvention. The process 900 can include selecting a contact (processportion 902) and analyzing contact information associated with thecontact (process portion 904). In certain embodiments, analyzing contactinformation can include analyzing at least one of a phone number, anaddress, and an affiliation (process portion 910).

For example, in some cases, a time zone can be determined or suggestedbased on the phone number (e.g., a country code and/or area code). Inmany cases, a time zone can be determined or suggested based on anaddress or physical location associated with the contact. The addresscan include a full address, including street address, city, state, andcountry or be a simple location (e.g., a city, a state, and/or country).In certain embodiments, if a time zone can not be determined from theaddress or location, a time zone for a nearby city (e.g., major city)and/or multiple time zones associated with an associated country can besuggested. In still other cases, a time zone can be determined orsuggested based on a contact's affiliation. For example, a contact'saffiliation can include an organization, company, or company group towhich the contact belongs or works. The affiliation can have a physicallocation (e.g., a location of a company) that can be used to determineor suggest a time zone. In certain situations, the contactidentification can include a general contact, for example, a group in acompany rather than an individual.

The process 900 can further include determining a time zone for thecontact based on the analysis of the contact information (processportion 906). In certain embodiments, determining a time zone for thecontact can include suggesting multiple time zones based on the analysisof the contact information (process portion 912) and selecting one ofthe multiple suggested time zones or manually entering a non-suggestedtime zone based on the manual analysis of the contact information(process portion 913). In still further embodiments, the process 900 caninclude storing the time zone for the contact (process portion 908). Ifthe time zone is stored, it can later be retrieved, for example, when acontact (e.g., a participant identification) is selected from a list ofcontacts during a scheduling process.

In certain cases, a contact may spend significant amounts of time in twoor more locations. Accordingly, it can be desirable to have multipletime zones associated with the contact. For example, when a user isscheduling an event, the user can be aware of the multiple time zonesassociated with the participant and/or choose between the multiple timezones for the participant based on knowing the participant is at aselected location.

Therefore, in certain embodiments, a computer-implemented process 1000for associating time zone information with a contact in an informationmanagement program application can include selecting a contact (processportion 1002) and analyzing contact information associated with thecontact (process portion 1004). The method can further includedetermining a first time zone for the contact based on the analysis ofthe contact information (process portion 1006) and determining analternate time zone for the contact based on the analysis of the contactinformation (process portion 1008). The method can still further includestoring the first time zone for the contact (process portion 1010) andstoring the alternate time zone for the contact (process portion 1012).

FIG. 11 is a partially schematic illustration of an informationmanagement program application display of contact information inaccordance with an embodiment of the invention. FIG. 12 is a partiallyschematic illustration of another information management programapplication display of contact information in accordance with anotherembodiment of the invention. In FIG. 11, a first time zone is associatedwith a first phone number, a first address, and a company with which thecontact is associated. An alternate time zone is associated with asecond phone number and a second address. Accordingly, if a user selectsthe contact as a participant during a scheduling process, the user isaware of the different time zones and, in certain embodiments, canchoose the appropriate time zone to use when scheduling an event. InFIG. 12, a first time zone and an alternate time zone are associatedwith the contact, but neither is displayed as being associated withspecific contact information. Again, a user that selects the contact ismade aware of the two time zones and, in certain embodiments, can choosethe appropriate time zone to use when scheduling an event. In otherembodiments, only one time zone is assigned to a contact. In certainembodiments, the time zones can be adjusted for changes between StandardTime and Daylight Savings Time.

As shown in FIG. 13, the computer-implemented scheduling process shownin FIG. 2 can further include coordinating the time range for the eventwith at least one of a user schedule and a participant schedule (processportion 1302). In certain embodiments, coordinating the time range forthe event with the user schedule can include annotating the event on theuser schedule for the selected time range (process portion 1304). Inother embodiments, coordinating the time range for the event with theparticipant schedule includes at least one of annotating the event onthe participant schedule for the selected time range, sending a requestthat the participant agree to participate in the event during theselected time range, and gaining agreement that the participant willparticipate in the event during the selected time range (process portion1306).

One feature of some of the embodiments described above is that a usercan schedule an event while being aware of availability informationrelative to time zones associated with each expected participant.Additionally, in certain cases, the user can be aware of certainscheduling preferences or time preference periods during which eventsshould or shouldn't be scheduled. These features can allow users toschedule events while being sensitive to time zone differences,availability, and other preferences. An advantage of these features isthat the scheduling process can be simplified and require lesscommunication/negotiation between the participants to find a suitabletime that accommodates time zone differences and/or schedulingpreferences as compared to current systems.

Another feature of some of the embodiments described above is that atime zone can be associated with a contact in an information managementprogram application by analyzing contact information. This feature canaid a user in determining time zone information without having toconduct research and/or querying the contact. An advantage of thisfeature is that time and effort can be saved when scheduling an event orattempting to determine a time zone for a contact.

From the foregoing, it will be appreciated that specific embodiments ofthe invention have been described herein for purposes of illustration,but that various modifications may be made without deviating from thespirit and scope of the invention. For example, aspects of the inventiondescribed in the context of particular embodiments may be combined oreliminated in other embodiments. Although advantages associated withcertain embodiments of the invention have been described in the contextof those embodiments, other embodiments may also exhibit suchadvantages. Additionally, none of the foregoing embodiments neednecessarily exhibit such advantages to fall within the scope of theinvention. Accordingly, the invention is not limited except as by theappended claims.

We claim:
 1. A system for scheduling with time zone information, thesystem comprising: a processor; and a system memory to storeinstructions that, based at least on execution by the processor, causethe processor to: select a participant identification; identify adifference between a participant time zone and a user time zone, wherethe participant time zone is associated with the participantidentification and the user time zone is associated with a user; andsend to a display for the user, a user calendar and a participantcalendar, the participant calendar offset from the user calendaraccounting for the difference between the participant time zone and theuser time zone so that a corresponding time range would be markedvisually in-line across the display for both the user calendar and theparticipant calendar.
 2. The system of claim 1, wherein the participantcalendar indicates at least one of a local time corresponding to theparticipant information and a time difference of the participant timezone relative to the user time zone.
 3. The system of claim 1, whereinthe user calendar and a plurality of participant calendars share thesame display of a time scale.
 4. The system of claim 1, wherein the usercalendar and a plurality of participant calendars each have their owndisplayed time scale.
 5. The system of claim 1, wherein the participanttime zone identification is listed next to the participantidentification.
 6. The system of claim 1, wherein the participantcalendar includes a marking that allow a user to visual determine thenon-availability for the participant during that the time indicated bythe marking.
 7. The system of claim 6, wherein the marking is at leastone of red, green, and amber colors.
 8. The system of claim 1, whereinthe participant identification is listed along the side of the display.9. The system of claim 1, wherein the selection of the participantidentification enables analysis of a contact information associated withthe participant identification.
 10. The system of claim 1, wherein atimes shown on the participant calendar is adjusted based on a timedifference of the participant time zone relative to the user time zoneso that a the time shown on the participant calendar is calculated anddisplayed as though the event were taking place in the user time zone.11. A method for scheduling with time zone information, the methodcomprising: selecting a participant identification; identifying adifference between a participant time zone and a user time zone, wherethe participant time zone is associated with the participantidentification and the user time zone is associated with a user; andsending to a display for the user, a user calendar and a participantcalendar, the participant calendar offset from the user calendaraccounting for the difference between the participant time zone and theuser time zone so that a contemporaneous time range would be markedvisually in-line across the display for both the user calendar and theparticipant calendar.
 12. The method of claim 11, wherein theparticipant calendar indicates at least one of a local timecorresponding to the participant information and a time difference ofthe participant time zone relative to the user time zone.
 13. The methodof claim 11, wherein the user calendar and a plurality of participantcalendars share the same display of a time scale.
 14. The method ofclaim 11, wherein the user calendar and a plurality of participantcalendars each have their own displayed time scale.
 15. The method ofclaim 11, wherein the participant time zone identification is listednext to the participant identification.
 16. The method of claim 11,wherein the participant calendar includes a marking that allow a user tovisual determine the non-availability for the participant during thatthe time indicated by the marking.
 17. The method of claim 16, whereinthe marking is at least one of red, green, and amber colors.
 18. Themethod of claim 11, wherein the participant identification is listedalong the side of the display.
 19. A system for scheduling with timezone information, the system comprising: a processor; and a systemmemory to store instructions that, based at least on execution by theprocessor, cause the processor to: select a participant identification;identify a difference between a participant time zone and a user timezone, where the participant time zone is associated with the participantidentification and the user time zone is associated with a user; andsend to a display for the user, a user calendar and a participantcalendar, the participant calendar aligned with the user calendar sothat a marking at a contemporaneous time and included in both the usercalendar and the participant calendar is displayed as offset by agraphical distance corresponding to the difference between theparticipant time zone and the user time zone.
 20. The system of claim19, wherein the user calendar and the participant calendar shares thesame display of a time scale.